One of a gotcha that I learned while working on SSIS development would be to checking the version of the SQL Server that will schedule the SSIS package and the Visual Studio version that compatible with the Server version. This MSDN article describe the list of compatibility https://msdn.microsoft.com/en-us/library/bb522577(v=sql.120).aspx
The table from the MSDN Article describe the “compatibility matrix” for the Server and Development tool required. For example, when I’m working on SQL Server 2012 environment, I need either Visual Studio 2010 or 2012 with SSDT, Visual Studio 2013 won’t be compatible for this.
Coming from Dynamics CRM development background, there are lots of things to learn from SQL Server world. So, hopefully my mistake could save up your time when developing SSIS, as at this moment I need to “convert” my package due to compatibility issue.
Work and Study book - Dynamics 365(CE) & Power Platform Blog 